Interacting with an automated teller machine using a user device

ABSTRACT

A device may receive an indication that an ATM transaction is to be conducted, display prompt(s) for a user to input user authentication credential information and to select an ATM transaction type, detect user input(s) that include a user authentication credential and a selection of a particular ATM transaction type, and receive, from an ATM device, a request to establish a communication session. The ATM device may include a sync button to initiate communicative coupling of the ATM device and the user device. The request may be based on a user selection of the sync button. The device may communicatively couple to the ATM device, and provide, to the ATM device, the user authentication credential and data regarding the particular ATM transaction type to cause the ATM device to perform the ATM transaction. The device may display information regarding the ATM transaction.

BACKGROUND

An automated teller machine (ATM) is an electronic device that permitsusers to perform various financial transactions, such as withdrawing anddepositing cash, obtaining account-related information, and/or the like.

SUMMARY

According to some possible implementations, a method may includereceiving, by a user device, an indication that an ATM transaction is tobe conducted; displaying, by the user device, one or more prompts, for auser to input user authentication credential information, and to selectan ATM transaction type, based on receiving the indication; detecting,by the user device, one or more user inputs that include a userauthentication credential and a selection of a particular ATMtransaction type after displaying the one or more prompts; receiving, bythe user device and from an ATM device, a request to establish acommunication session after detecting the one or more user inputs, theATM device including a sync button to initiate communicative coupling ofthe ATM device and the user device, the request being based on a userselection of the sync button; communicatively coupling, by the userdevice, to the ATM device based on receiving the request; providing, bythe user device, to the ATM device, and based on communicativelycoupling to the ATM device, the user authentication credential and dataregarding the particular ATM transaction type to cause the ATM device toperform the ATM transaction; and displaying, by the user device,information regarding the ATM transaction after providing the userauthentication credential and the data regarding the particular ATMtransaction type.

According to some possible implementations, a non-transitorycomputer-readable medium may store instructions, the instructions mayinclude one or more instructions that, when executed by one or moreprocessors of a user device, cause the one or more processors toreceive, from an ATM device, a pairing instruction, the ATM deviceincluding a sync button to initiate pairing of the ATM device and theuser device, the pairing instruction being based on a user selection ofthe sync button; communicatively couple to the ATM device based on thepairing instruction; receive, from the ATM device, a request for userauthentication credential information after communicatively coupling tothe ATM device; cause a first prompt, for a user to input a userauthentication credential, to be presented based on receiving therequest; detect a user input that includes the user authenticationcredential after causing the first prompt to be presented; provide, tothe ATM device, the user authentication credential based on detectingthe user input; obtain, from the ATM device, an authorization to proceedwith an ATM transaction after providing the user authenticationcredential; cause a second prompt, for the user to select an ATMtransaction type, to be presented based on obtaining the authorization;detect a user selection of a particular ATM transaction type aftercausing the second prompt to be presented; and provide, to the ATMdevice, information regarding the particular ATM transaction type, basedon detecting the user selection, to cause the ATM device to perform theATM transaction.

According to some possible implementations, an ATM device may include adevice body, the device body including a sync button to initiatewireless communications with external user devices; a communicationinterface configured to communicatively couple to external user devicesbased on user selection of the sync button; one or more memories; andone or more processors communicatively coupled to the one or morememories and the communication interface, the one or more processorsbeing configured to cause the communication interface to provide, to anexternal user device, a first instruction to prompt a user of theexternal user device to input personal identification number (PIN)information relating to an account associated with the user; receive,via the communication interface, a PIN provided by the external userdevice after causing the communication interface to provide the firstinstruction; perform an action to validate the PIN with respect to theaccount; cause the communication interface to provide, to the externaluser device and based on validating the PIN, a second instruction toprompt the user to specify transaction information; and perform an ATMtransaction based on the transaction information.

BRIEF DESCRIPTION OF THE DRAWINGS

FIGS. 1A-1I are diagrams of an overview of an example implementationdescribed herein;

FIG. 2 is a diagram of an example environment in which systems and/ormethods, described herein, may be implemented;

FIG. 3 is a diagram of example components of one or more devices of FIG.2;

FIG. 4 is a flow chart of an example process for using a user device tointeract with an ATM device;

FIGS. 5A and 5B are diagrams of an example process for using a userdevice to interact with an ATM device; and

FIG. 6 is a flow chart of an example process for using an ATM device tointeract with a user device to facilitate a transaction.

DETAILED DESCRIPTION

The following detailed description of example implementations refers tothe accompanying drawings. The same reference numbers in differentdrawings may identify the same or similar elements.

In many cases, a user must insert a transaction card into (or swipe atransaction card through) a card reader of an ATM device, and enter acorresponding PIN using a touch screen display or a keypad of the ATMdevice, in order to conduct an ATM transaction. This introduces thepossibility of theft of the user's account data, however, since amalicious user can easily install skimmers, cameras, and/or the like toillicitly capture the user's PIN or transaction card data. Furthermore,user interface components of a typical ATM device, such as a touchscreen display and a keypad, are subject to wear and tear, due tofrequent use, which increases the costs of maintaining the ATM device.

Some implementations, described herein, provide a user device that iscapable of functioning as a user interface for an ATM device. In someimplementations, the user device is capable of permitting a user toinput the user's authentication credential (e.g., personalidentification number (PIN)) and make ATM transaction selection(s), andproviding the authentication credential, and information regarding theATM transaction selection(s), to the ATM device to performtransaction(s). In some implementations, the ATM device lacks userinterface components, such as a touch screen display, a keypad, and/orthe like, that are typically included in an ATM device. In someimplementations, the ATM device may include a user-selectablesynchronization (“sync”) button that, when selected, enables the ATMdevice to pair with the user device, and one or more illuminationcomponents (e.g., light-emitting diodes (LEDs)) that may be used toprovide user notifications.

In this way, an ATM device manufacturer can provide an ATM device thatincludes fewer components, which simplifies the design and manufacturingof the ATM device, thereby reducing costs. In addition, this reduces oreliminates the possibility of wear and tear of the ATM device that wouldotherwise occur due to frequent user interaction with user interfacecomponents. Furthermore, enabling a user device (e.g., that is externalto an ATM device) to function as a user interface of the ATM devicereduces or eliminates a need for a user to input the user's PIN directlyto the ATM device, which reduces or eliminates the possibility of theft(e.g., via skimmers, cameras, and/or the like) of user account data andimproves the overall security of ATM transactions.

FIGS. 1A-1I are diagrams of an overview of an example implementation 100described herein. Example implementation 100 may include a user device,an ATM card, and an ATM device. The ATM card may include a transactioncard, such as a debit card, a credit card, and/or the like. The ATMdevice may be display-free—that is, the ATM device may not include adisplay, such as a touch screen display. In some implementations, theATM device may include no user input components other than a sync button(e.g., described in more detail below).

In some implementations, the user device may include anapplication—e.g., an ATM transaction application—configured to enablethe user device to interact with ATM devices. In some implementations,the application, when executed by one or more processors of the userdevice, may cause the one or more processors to present a user interface(e.g., various user interface screens) that permits a user to input userauthentication credential information, such as a PIN, and make ATMtransaction selection(s), prior to proceeding to the ATM device toconduct the transaction(s).

As shown in FIG. 1A, and as shown by reference number 102, the userdevice may detect that a user wants to conduct an ATM transaction. Forexample, the user device may detect a presence of the ATM card (e.g.,via near-field communication (NFC) and/or the like), and determine thatthe user wants to conduct an ATM transaction based on detecting thepresence of the ATM card. As another example, the user device may detect(e.g., via the user interface) a user input indicating that the userwants to conduct an ATM transaction.

As shown in FIG. 1B, and as shown by reference number 104, the userdevice may prompt (e.g., via the user interface) the user for a PIN, anddetect a PIN entry. As shown in FIG. 1C, and as shown by referencenumber 106, the user device may store the PIN, and display a userinterface screen that prompts the user to select one or more ATMtransactions that the user wants to conduct. The ATM transactions mayinclude, for example, a withdrawal of funds from the user's account, adeposit of funds into the user's account, a request for balanceinformation regarding the user's account, and/or the like. As shown byreference number 108, the user may make one or more ATM transactionselection(s).

As shown in FIG. 1D, and as shown by reference number 110, the user mayproceed to the ATM device with the user device. In some implementations,the user may access the ATM transaction application on the user devicewhen the user is near the ATM device. In some implementations, the ATMtransaction application may automatically execute when the user deviceis near the ATM device. As one example, the user device mayautomatically cause the ATM transaction application to execute when theuser device is located within a threshold distance from the ATM device(e.g., based on a current location of the user device (e.g., as detectedby a location-based receiver included in the user device) relative to aknown location of the ATM device), when the user device detects one ormore signals broadcasted by the ATM device, when the user devicereceives, from the ATM device, response(s) to signals broadcasted by theuser device, and/or the like. As shown by reference number 112, the userdevice and the ATM device may pair with one another. In someimplementations, the ATM device may include a wireless transceiver(e.g., a Bluetooth-based communication interface and/or the like), and async button that, when selected by a user, enables the wirelesstransceiver to initiate wireless communications, such as tocommunicatively couple with a user device. Here, for example, the usermay select the sync button (e.g., by pressing the sync button), and theATM device may communicatively couple with the user device based on theselection.

In situations where there are multiple ATM devices near one another, andto avoid the possibility of a user device pairing with an unintended ATMdevice (e.g., an ATM device that is not directly in front of the user ofthe user device) and a user of the user device mistakenly conducting atransaction with the unintended ATM device, each of the ATM devices maybe associated with a unique identifier (e.g., a name or a device ID thatincludes alphanumeric characters), may be visibly marked (e.g., on asurface of a body of the ATM device in the form of a tag, a plate, anetching (e.g., a laser etching and/or the like), and/or the like) withthe unique identifier, and may broadcast a pairing signal (e.g., aBluetooth-based signal) containing the unique identifier. Here, even ifa first user, of a first user device, might select the sync button of afirst ATM device, and a second user, of a second user device, mightsimultaneously (or near simultaneously) select the sync button of asecond ATM device, each of the first ATM device and the second ATMdevice may broadcast the pairing signal, each of the first user deviceand the second user device may receive such signals and display thecorresponding unique identifiers (e.g., as two user-selectable icons)for user selection, and each of the first user and the second user mayeasily select the appropriate unique identifier based on the visiblemarkings on the first ATM device and the second ATM device.

In some implementations, the ATM device may be configured to terminate acommunication session with the user device after the selectedtransaction(s) are completed. In some implementations, the ATM devicemay permit a user to end a communication session early by selecting thesync button during the communication session. Additionally, oralternatively, the user device may provide (e.g., via the userinterface) a user-selectable input that permits a user to selectivelyend a communication session early.

In some implementations, the ATM device may include one or more LEDsthat can be used to provide one or more status notifications to users.For example, the ATM device may cause an LED to illuminate when the ATMdevice is successfully paired with a user device. This may, for example,permit a user (e.g., after selecting the sync button and prior to theuser's user device providing PIN information to the ATM device forauthentication or validation) to ensure, via a visual cue, that theuser's user device is paired with an intended ATM device. In addition,this reduces or eliminates the possibility of a user's accountinformation being compromised by thieves, such as via spoofing devicesthat copy and utilize ATM identifier information to deceive users tosync the users' user devices with the spoofing devices.

In some implementations, the ATM device may cause an LED to illuminatein different manners (e.g., illuminate and remain illuminated fordifferent periods of time, illuminate at different intensities,illuminate in different colors, and/or the like), depending on whetherdevice pairing is successful, whether a correct PIN is inputted, whetherthe ATM device is out of cash, whether the ATM device is functioningproperly, and/or the like. As some examples, the ATM device may cause anLED to illuminate in green when a user's PIN is validated, illuminate inred if an inputted PIN is incorrect, and/or periodically illuminate(e.g., blink) in red if the ATM device is malfunctioning and/or out ofcash.

In some implementations, and to thwart attempts by a malicious user to“listen in” and/or record data transmissions between the ATM device andother user devices, the ATM device may employ an encryption protocol(e.g., a hypertext transfer protocol secure (HTTPS)-based protocoland/or the like) to secure the data transmissions.

In some implementations, the ATM device may be configured to prevent aman-in-the-middle (MITM) attack, where a malicious user alters the ATMdevice's unique identifier to display a unique identifier that isassociated with the malicious user's own user device—e.g., a maliciousdevice—such that the malicious device pairs with other user devicesattempting to communicatively couple to the ATM device (i.e., in orderto function as a pathway between the ATM device and the other userdevices), and digitally skims, or steals, data transmitted from theother user devices. To prevent such attacks, the ATM device may beconfigured to limit a quantity of times that each user device maycommunicatively couple to the ATM device per unit time (e.g., up to athreshold quantity of connections with the ATM device per day, per hour,and/or the like), limit a duration of each communication session with auser device (e.g., by automatically terminating a communication sessionupon, or after, completion of a transaction, by automaticallyterminating a communication session upon, or after, a threshold periodof time has elapsed from when the communication session is established,and/or the like). In this way, if a malicious device attempts tocommunicatively couple to the ATM device after a connection limit hasbeen reached, and/or the like, the ATM device may refuse to furthercommunicatively couple with the malicious device.

In some implementations, the ATM device may be configured to restrict auser device from communicatively coupling to the ATM device for morethan a single transaction account. That is, if a malicious devicecommunicatively couples to the ATM device for a first transactionaccount associated with a first user, and subsequently attempts tocommunicatively couple to the ATM device for a second transactionaccount associated with a second user, the ATM device may refuse tocommunicatively couple with the malicious device. In someimplementations, the second user's user device may receive an error(e.g., from the ATM device) when the second user attempts toauthenticate (via the malicious device). In some implementations, theerror may include information indicating that a different user deviceneeds to be used. Alternatively, the error may not include anyadditional information so as to obscure a root cause of the error. Insome implementations, a user may be permitted to reset, or otherwisedisassociate, the user's transaction account from a previouslyassociated user device. In some implementations, the user's user devicemay be automatically disassociated from the user's transaction accountafter a predefined period of time, such as after one day, after oneweek, after one month, and/or the like.

As shown in FIG. 1E, and as shown by reference number 114, the userdevice may provide, to the ATM device, the user's PIN for validation,and information regarding the ATM transaction selection(s) made by theuser (e.g., information regarding whether and how much funds are to bewithdrawn, whether and how much funds are to be deposited, whetherbalance information is to be provided, and/or the like).

As shown by reference number 116, the ATM device may validate the user'sPIN. In some implementations, the ATM device may communicate with one ormore server devices (e.g., validation device(s)) to validate the PIN. Asshown by reference number 118, the ATM device may provide, to the userdevice, an indication that the user's PIN is validated. In someimplementations, the user device may display (e.g., via the userinterface) a notification to the user indicating that the user's PIN hasbeen validated.

As shown in FIG. 1F, and as shown by reference number 120, thetransaction may then be conducted, depending on user's selected ATMtransaction(s). As an example, in a case where the user's selected ATMtransaction is to deposit cash, deposit a check, and/or the like, theuser device may prompt the user to insert cash and/or check(s) into theATM device. In some implementations, the indication that the user's PINis validated (reference number 118) may trigger the user device toprompt the user to insert the cash and/or the check(s). Additionally, oralternatively, and in some implementations, the ATM device may provide,to the user device, a separate instruction to prompt the user to insertthe cash and/or the check(s).

As another example, in a case where the user's selected ATM transactionis to withdraw cash, the ATM device may dispense the appropriate amountof cash, and the user device may prompt the user to obtain the cash fromthe ATM device. In some implementations, the ATM device may provide, tothe user device, an instruction to prompt the user to obtain the cashfrom the ATM device. As yet another example, in a case where the user'sselected ATM transaction is to check balance information, the ATM devicemay provide, to the user device, information regarding a balance of theuser's account, which the user device may display to the user.

As described above, the user device may provide a user interface thatpermits a user to input a PIN and to make ATM transaction selection(s),prior to proceeding to the ATM device to conduct the transaction(s).Alternatively, and in some implementations, the user device and the ATMdevice may communicatively couple, or pair, with one another, afterwhich the ATM device may cause the user device to present the varioususer interface screens relating to PIN entry and ATM transactionselection.

As shown in FIG. 1G, and as shown by reference number 152, the user mayproceed to the ATM device with the user device. As shown by referencenumber 154, the user device and the ATM device may pair with oneanother. For example, the user may select the sync button of the ATMdevice, and the user device and the ATM device may pair with one anotherbased on the user's selection, as described above with respect toreference number 112.

As shown in FIG. 1H, and as shown by reference number 156, the ATMdevice may instruct the user device to prompt the user for a PIN. Insome implementations, the ATM device may include a transaction cardreader (e.g., a card insertion or swiping mechanism, a contactless cardreading mechanism, and/or the like). In such cases, the ATM device mayinstruct the user device to prompt the user for a PIN based on the userinserting the ATM card into the transaction card reader, swiping the ATMcard through the transaction card reader, and/or tapping the ATM card on(or placing the ATM card near) the transaction card reader. In someimplementations, the ATM device may not include a transaction cardreader. In such cases, the ATM device may instruct the user device toprompt the user for a PIN based on information, regarding the ATM card,provided by the user device (e.g., after the user device detects the ATMcard via NFC, based on card information pre-stored in memory in the userdevice, and/or the like).

As shown by reference number 158, the user device may display a userinterface that prompts the user for a PIN, and detect a PIN entry. Asshown by reference number 160, the user device may provide, to the ATMdevice, the user's PIN for validation. As shown by reference number 162,the ATM device may validate the user's PIN.

As shown in FIG. 1I, and as shown by reference number 164, the ATMdevice may provide, to the user device, an indication that the user'sPIN is validated. As shown by reference number 166, the user device maydisplay a user interface that prompts the user to select one or more ATMtransactions that the user wants to conduct. In some implementations,the indication that the user's PIN is validated (reference number 164)may trigger the user device to prompt the user to select one or more ATMtransactions. Additionally, or alternatively, and in someimplementations, the ATM device may provide, to the user device, aseparate instruction to prompt the user to select one or more ATMtransactions.

As shown by reference number 168, the user may make one or more ATMtransaction selections via the user interface on the user device. Asshown by reference number 170, the user device may provide, to the ATMdevice, information regarding the ATM transaction selection(s) to causethe ATM device to perform the corresponding transaction(s) (e.g., asdescribed above with respect to reference number 120).

In some implementations, and although not shown, the ATM device may beassociated with, and communicatively coupled to (e.g., via a wiredconnection and/or a wireless connection), a dedicated user device thatenables a user to interact with the ATM device to conduct transactionsin manners similar to those described above with respect to FIGS. 1A-1I.In some implementations, the dedicated user device may be disposed inproximity to (e.g., disposed within a short distance, such as withinseveral meters and/or the like, from) the ATM device, and may bepre-sync′d with the ATM device. In some implementations, the dedicateduser device may be removably attached to a surface (e.g., a wall nearthe ATM device, a surface of the body of the ATM device, and/or thelike), which permits a user, when conducting a transaction at the ATMdevice, to position and/or orient the dedicated user device according tothe user's preference, height, and/or the like.

In this way, an ATM device manufacturer can provide an ATM device thatincludes fewer components, which simplifies the design and manufacturingof the ATM device, thereby reducing costs. In addition, this reduces oreliminates the possibility of wear and tear of the ATM device that wouldotherwise occur due to frequent user interaction with user interfacecomponents. Furthermore, enabling a user device (e.g., that is externalto an ATM device) to function as a user interface of the ATM devicereduces or eliminates a need for a user to input the user's PIN directlyto the ATM device, which reduces or eliminates the possibility of theft(e.g., via skimmers, cameras, and/or the like) of user account data andimproves the overall security of ATM transactions.

As indicated above, FIGS. 1A-1I are provided merely as examples. Otherexamples are possible and may differ from what was described with regardto FIGS. 1A-1I.

FIG. 2 is a diagram of an example environment 200 in which systemsand/or methods, described herein, may be implemented. As shown in FIG.2, environment 200 may include an ATM device 205 that includes one ormore input/output components 210, one or more processors 215, one ormore memories 220, and a communication interface 225. Environment 200may also include one or more validation devices 230, a user device 240,a transaction card 250, and a network 260. Devices of environment 200may interconnect via wired connections, wireless connections, or acombination of wired and wireless connections.

ATM device 205 includes one or more devices capable of performingvarious types of financial transactions, such as a cash withdrawal, amoney deposit (e.g., a check or cash deposit), a money transfer (e.g., atransfer from one bank account to another bank account), access toinformation related to an account (e.g., a bank account, a checkingaccount, a credit card account, etc.), and/or the like. For example, ATMdevice 205 may include an ATM, an automated banking machine (ABM), acash point, a Cashline®, a Minibank®, a cash machine, a Tyme® machine, acash dispenser, a Bankomat®, a Bancomat®, and/or a similar type ofdevice.

Input/output component 210 includes one or more devices capable of beingused to input information into, and/or output information from, ATMdevice 205. For example, input/output component 210 may include a userinput component (e.g., a sync button, as described elsewhere herein)capable of enabling (e.g., when the user input component is selected bya user) ATM device 205 to communicatively couple to (e.g., pair with)user devices, such as user device 240. As another example, input/outputcomponent 210 may include a speaker, an indicator light (e.g., an LED,as described elsewhere herein, and/or the like), a vibrating component,and/or the like that can output information associated with ATM device205 and/or an action to be performed in connection with an account.

Processor 215 includes one or more types of processing componentscapable of being programmed to perform a function, such as one or moreoperations described elsewhere herein. For example, processor 215 mayperform process 400 of FIG. 4, process 500 of FIGS. 5A and 5B, process600 of FIG. 6, and/or the like. In some implementations, processor 215may correspond to processor 320, described in more detail below inconnection with FIG. 3.

Memory 220 includes one or more types of memories capable of storinginformation. In some implementations, memory 220 may store informationassociated with performing one or more operations described elsewhereherein. For example, memory 220 may store information to be used (e.g.,by processor 215) to perform process 400 of FIG. 4, process 500 of FIGS.5A and 5B, process 600 of FIG. 6, and/or the like. In someimplementations, memory 220 may correspond to memory 330, described inmore detail below in connection with FIG. 3.

Communication interface 225 includes one or more types of communicationinterfaces that allow ATM device 205 to communicate with other devices(e.g., validation device 230, user device 240, transaction card 250,and/or the like), such as via a wired connection, a wireless connection,or a combination of wired and wireless connections. For example,communication interface 225 may be used to read information fromtransaction card 250, to transmit information to, or receive informationfrom, validation device 230 and/or user device 240, and/or the like. Insome implementations, communication interface 225 may correspond tocommunication interface 370, described in more detail below inconnection with FIG. 3.

Validation device 230 includes one or more devices capable of validatinguser authentication credential information for account access. Forexample, validation device 230 may include a server, a cloud computingdevice, a transaction backend, or another type of computing device.

User device 240 includes one or more devices capable of receiving,processing, and/or providing data relating to ATM device 205 and/ortransaction card 250. For example, user device 240 may include a smartphone, a tablet computer, a laptop computer, a desktop computer, awearable device, and/or the like. In some implementations, user device240 may be capable of functioning as a user interface of ATM device 205,as described elsewhere herein.

Transaction card 250 includes a transaction card that can be used tocomplete a transaction and/or access account information. For example,transaction card 250 may include a credit card, a debit card, an ATMcard, a stored-value card, a fleet card, a transit card, an access card,a virtual card implemented on user device 240, and/or the like.Transaction card 250 may be capable of storing and/or communicating datafor a point-of-sale (PoS) transaction and/or an ATM transaction. Forexample, transaction card 250 may store and/or communicate data,including account information (e.g., an account identifier, a cardholderidentifier, etc.), expiration information of transaction card 250 (e.g.,information identifying an expiration month and/or year of transactioncard 250), banking information (e.g., a routing number of a bank, a bankidentifier, etc.), transaction information (e.g., a payment token),and/or the like. For example, to store and/or communicate the data,transaction card 250 may include a magnetic strip and/or an integratedcircuit (IC) chip (e.g., a EUROPAY®, MASTERCARD®, or VISA® (EMV) chip).Additionally, or alternatively, transaction card 250 may include anantenna to communicate data associated with transaction card 250. Theantenna may be a passive radio frequency (RF) antenna, an active RFantenna, and/or a battery-assisted RF antenna. In some implementations,transaction card 250 may be a smart transaction card, capable ofcommunicating wirelessly (e.g., via Bluetooth, Bluetooth Low Energy(BLE), NFC, and/or the like) with ATM device 205.

Network 260 includes one or more wired and/or wireless networks. Forexample, network 260 may include a cellular network (e.g., a long-termevolution (LTE) network, a code division multiple access (CDMA) network,a 3G network, a 4G network, a 5G network, another type of nextgeneration network, etc.), a public land mobile network (PLMN), a localarea network (LAN), a wide area network (WAN), a metropolitan areanetwork (MAN), a telephone network (e.g., the Public Switched TelephoneNetwork (PSTN)), a private network, an ad hoc network, an intranet, theInternet, a fiber optic-based network, a cloud computing network, and/orthe like, and/or a combination of these or other types of networks.

The number and arrangement of devices and networks shown in FIG. 2 areprovided as an example. In practice, there may be additional devicesand/or networks, fewer devices and/or networks, different devices and/ornetworks, or differently arranged devices and/or networks than thoseshown in FIG. 2. Furthermore, two or more devices shown in FIG. 2 may beimplemented within a single device, or a single device shown in FIG. 2may be implemented as multiple, distributed devices. Additionally, oralternatively, a set of devices (e.g., one or more devices) ofenvironment 200 may perform one or more functions described as beingperformed by another set of devices of environment 200.

FIG. 3 is a diagram of example components of a device 300. Device 300may correspond to ATM device 205, validation device(s) 230, user device240, and/or transaction card 250. In some implementations, ATM device205, validation device(s) 230, user device 240, and/or transaction card250 may include one or more devices 300 and/or one or more components ofdevice 300. As shown in FIG. 3, device 300 may include a bus 310, aprocessor 320, a memory 330, a storage component 340, an input component350, an output component 360, and a communication interface 370.

Bus 310 includes a component that permits communication among thecomponents of device 300. Processor 320 is implemented in hardware,firmware, or a combination of hardware and software. Processor 320 is acentral processing unit (CPU), a graphics processing unit (GPU), anaccelerated processing unit (APU), a microprocessor, a microcontroller,a digital signal processor (DSP), a field-programmable gate array(FPGA), an application-specific integrated circuit (ASIC), or anothertype of processing component. In some implementations, processor 320includes one or more processors capable of being programmed to perform afunction. Memory 330 includes a random access memory (RAM), a read onlymemory (ROM), and/or another type of dynamic or static storage device(e.g., a flash memory, a magnetic memory, and/or an optical memory) thatstores information and/or instructions for use by processor 320.

Storage component 340 stores information and/or software related to theoperation and use of device 300. For example, storage component 340 mayinclude a hard disk (e.g., a magnetic disk, an optical disk, amagneto-optic disk, and/or a solid state disk), a compact disc (CD), adigital versatile disc (DVD), a floppy disk, a cartridge, a magnetictape, and/or another type of non-transitory computer-readable medium,along with a corresponding drive.

Input component 350 includes a component that permits device 300 toreceive information, such as via user input (e.g., a touch screendisplay, a keyboard, a keypad, a mouse, a button, a switch, and/or amicrophone). Additionally, or alternatively, input component 350 mayinclude a sensor for sensing information (e.g., a global positioningsystem (GPS) component, an accelerometer, a gyroscope, and/or anactuator). Output component 360 includes a component that providesoutput information from device 300 (e.g., a display, a speaker, and/orone or more light-emitting diodes (LEDs)).

Communication interface 370 includes a transceiver-like component (e.g.,a transceiver and/or a separate receiver and transmitter) that enablesdevice 300 to communicate with other devices, such as via a wiredconnection, a wireless connection, or a combination of wired andwireless connections. Communication interface 370 may permit device 300to receive information from another device and/or provide information toanother device. For example, communication interface 370 may include anEthernet interface, an optical interface, a coaxial interface, aninfrared interface, a radio frequency (RF) interface, a universal serialbus (USB) interface, a wireless local area interface, a cellular networkinterface, and/or the like.

Device 300 may perform one or more processes described herein. Device300 may perform these processes based on processor 320 executingsoftware instructions stored by a non-transitory computer-readablemedium, such as memory 330 and/or storage component 340. Acomputer-readable medium is defined herein as a non-transitory memorydevice. A memory device includes memory space within a single physicalstorage device or memory space spread across multiple physical storagedevices.

Software instructions may be read into memory 330 and/or storagecomponent 340 from another computer-readable medium or from anotherdevice via communication interface 370. When executed, softwareinstructions stored in memory 330 and/or storage component 340 may causeprocessor 320 to perform one or more processes described herein.Additionally, or alternatively, hardwired circuitry may be used in placeof or in combination with software instructions to perform one or moreprocesses described herein. Thus, implementations described herein arenot limited to any specific combination of hardware circuitry andsoftware.

The number and arrangement of components shown in FIG. 3 are provided asan example. In practice, device 300 may include additional components,fewer components, different components, or differently arrangedcomponents than those shown in FIG. 3. Additionally, or alternatively, aset of components (e.g., one or more components) of device 300 mayperform one or more functions described as being performed by anotherset of components of device 300.

FIG. 4 is a flow chart of an example process 400 for using a user deviceto interact with an ATM device. In some implementations, one or moreprocess blocks of FIG. 4 may be performed by user device 240. In someimplementations, one or more process blocks of FIG. 4 may be performedby another device or a group of devices separate from or including userdevice 240, such as ATM device 205, validation device 230, and/ortransaction card 250.

As shown in FIG. 4, process 400 may include receiving, by a user device(e.g., user device 240), an indication that an ATM transaction is to beconducted (block 410). For example, user device 240 (e.g., usingprocessor 320, memory 330, storage component 340, input component 350,communication interface 370, and/or the like) may receive an indicationthat an ATM transaction is to be conducted, as described above inconnection with FIGS. 1A-1I.

As further shown in FIG. 4, process 400 may include displaying, by theuser device, one or more prompts, for a user to input userauthentication credential information, and to select an ATM transactiontype, based on receiving the indication (block 420). For example, userdevice 240 (e.g., using processor 320, memory 330, storage component340, output component 360, communication interface 370, and/or the like)may display one or more prompts, for a user to input user authenticationcredential information, and to select an ATM transaction type, based onreceiving the indication, as described above in connection with FIGS.1A-1I.

As further shown in FIG. 4, process 400 may include detecting, by theuser device, one or more user inputs that include a user authenticationcredential and a selection of a particular ATM transaction type afterdisplaying the one or more prompts (block 430). For example, user device240 (e.g., using processor 320, memory 330, storage component 340, inputcomponent 350, communication interface 370, and/or the like) may detectone or more user inputs that include a user authentication credentialand a selection of a particular ATM transaction type after displayingthe one or more prompts, as described above in connection with FIGS.1A-1I.

As further shown in FIG. 4, process 400 may include receiving, by theuser device and from an ATM device (e.g., ATM device 205), a request toestablish a communication session after detecting the one or more userinputs, where the ATM device includes a sync button to initiatecommunicative coupling of the ATM device and the user device, and wherethe request is based on a selection of the sync button (block 440). Forexample, user device 240 (e.g., using processor 320, memory 330, storagecomponent 340, communication interface 370, and/or the like) mayreceive, from ATM device 205, a request to establish a communicationsession after detecting the one or more user inputs, where ATM device205 includes a sync button to initiate communicative coupling of ATMdevice 205 and user device 240, and where the request is based on a userselection of the sync button, as described above in connection withFIGS. 1A-1I.

As further shown in FIG. 4, process 400 may include communicativelycoupling, by the user device, to the ATM device based on receiving therequest (block 450). For example, user device 240 (e.g., using processor320, memory 330, storage component 340, communication interface 370,and/or the like) may communicatively couple to ATM device 205 based onreceiving the request, as described above in connection with FIGS.1A-1I.

As further shown in FIG. 4, process 400 may include providing, by theuser device, to the ATM device, and based on communicatively coupling tothe ATM device, the user authentication credential and data regardingthe particular ATM transaction type to cause the ATM device to performthe ATM transaction (block 460). For example, user device 240 (e.g.,using processor 320, memory 330, storage component 340, communicationinterface 370, and/or the like) may provide, to ATM device 205, andbased on communicatively coupling to ATM device 205, the userauthentication credential and data regarding the particular ATMtransaction type to cause ATM device 205 to perform the ATM transaction,as described above in connection with FIGS. 1A-1I.

As further shown in FIG. 4, process 400 may include displaying, by theuser device, information regarding the ATM transaction after providingthe user authentication credential and the data regarding the particularATM transaction type (block 470). For example, user device 240 (e.g.,using processor 320, memory 330, storage component 340, output component360, communication interface 370, and/or the like) may displayinformation regarding the ATM transaction after providing the userauthentication credential and the data regarding the particular ATMtransaction type, as described above in connection with FIGS. 1A-1I.

Process 400 may include additional implementations, such as any singleimplementation or any combination of implementations described belowand/or in connection with one or more other processes describedelsewhere herein.

In some implementations, the ATM device may lack user interfacecomponents other than the sync button. In some implementations,receiving the indication may include detecting, by the user device, apresence of an ATM transaction card (e.g., transaction card 250), orreceiving, by the user device, a user command to conduct the ATMtransaction using information associated with the ATM transaction card.

In some implementations, the ATM device may include an illuminationcomponent configured to provide user notifications. In someimplementations, the user notifications may relate to successfulcommunicatively coupling of the user device and the ATM device,validation of the user authentication credential, an availability offunds in the ATM device, or an operating status of the ATM device.

In some implementations, the user device may initiate a timer afterdetecting the one or more user inputs, and determine whether the timerhas expired prior to providing the user authentication credential andthe data regarding the particular ATM transaction type. In someimplementations, providing the user authentication credential and thedata regarding the particular ATM transaction type may include providingthe user authentication credential and the data regarding the particularATM transaction type further based on determining that the timer has notexpired.

In some implementations, the ATM device may include a card readingmechanism. In some implementations, the ATM device may lack userinterface components other than the sync button and the card readingmechanism. In some implementations, the user device may receive, fromthe ATM device, the information regarding the ATM transaction. In someimplementations, displaying the information regarding the ATMtransaction may include displaying the information regarding the ATMtransaction based on receiving the information regarding the ATMtransaction.

In some implementations, the information regarding the ATM transactionmay include an instruction to the user to insert one or more financialinstruments into the ATM device, or to retrieve one or more financialinstruments from the ATM device, depending on the particular ATMtransaction type.

Although FIG. 4 shows example blocks of process 400, in someimplementations, process 400 may include additional blocks, fewerblocks, different blocks, or differently arranged blocks than thosedepicted in FIG. 4. Additionally, or alternatively, two or more of theblocks of process 400 may be performed in parallel.

FIGS. 5A and 5B are diagrams of an example process 500 for using a userdevice to interact with an ATM device. In some implementations, one ormore process blocks of FIGS. 5A and 5B may be performed by user device240. In some implementations, one or more process blocks of FIGS. 5A and5B may be performed by another device or a group of devices separatefrom or including user device 240, such as ATM device 205, validationdevice 230, and/or transaction card 250.

In some implementations, a non-transitory computer-readable medium maystore instructions. In some implementations, the instructions mayinclude one or more instructions that, when executed by one or moreprocessors of a user device (e.g., user device 240), cause the one ormore processors to perform process 500.

As shown in FIG. 5A, process 500 may include receiving, from an ATMdevice (e.g., ATM device 205), a pairing instruction, where the ATMdevice may include a sync button to initiate pairing of the ATM deviceand the user device, and where the pairing instruction may be based on auser selection of the sync button (block 505). For example, user device240 (e.g., using processor 320, memory 330, storage component 340,communication interface 370, and/or the like) may receive, from ATMdevice 205, a pairing instruction, where ATM device 205 may include async button to initiate pairing of ATM device 205 and user device 240,and where the pairing instruction may be based on a user selection ofthe sync button, as described above in connection with FIGS. 1A-1I.

As further shown in FIG. 5A, process 500 may include communicativelycoupling to the ATM device based on the pairing instruction (block 510).For example, user device 240 (e.g., using processor 320, memory 330,storage component 340, communication interface 370, and/or the like) maycommunicatively couple to ATM device 205 based on the pairinginstruction, as described above in connection with FIGS. 1A-1I.

As further shown in FIG. 5A, process 500 may include receiving, from theATM device, a request for user authentication credential informationafter communicatively coupling to the ATM device (block 515). Forexample, user device 240 (e.g., using processor 320, memory 330, storagecomponent 340, communication interface 370, and/or the like) mayreceive, from ATM device 205, a request for user authenticationcredential information after communicatively coupling to ATM device 205,as described above in connection with FIGS. 1A-1I.

As further shown in FIG. 5A, process 500 may include causing a firstprompt, for a user to input a user authentication credential, to bepresented based on receiving the request (block 520). For example, userdevice 240 (e.g., using processor 320, memory 330, storage component340, output component 360, communication interface 370, and/or the like)may cause a first prompt, for a user to input a user authenticationcredential, to be presented based on receiving the request, as describedabove in connection with FIGS. 1A-1I.

As further shown in FIG. 5A, process 500 may include detecting a userinput that includes the user authentication credential after causing thefirst prompt to be presented (block 525). For example, user device 240(e.g., using processor 320, memory 330, storage component 340, inputcomponent 350, communication interface 370, and/or the like) may detecta user input that includes the user authentication credential aftercausing the first prompt to be presented, as described above inconnection with FIGS. 1A-1I.

As further shown in FIG. 5A, process 500 may include providing, to theATM device, the user authentication credential based on detecting theuser input (block 530). For example, user device 240 (e.g., usingprocessor 320, memory 330, storage component 340, communicationinterface 370, and/or the like) may provide, to ATM device 205, the userauthentication credential based on detecting the user input, asdescribed above in connection with FIGS. 1A-1I.

As shown in FIG. 5B, process 500 may include obtaining, from the ATMdevice, an authorization to proceed with an ATM transaction afterproviding the user authentication credential (block 535). For example,user device 240 (e.g., using processor 320, memory 330, storagecomponent 340, communication interface 370, and/or the like) may obtain,from ATM device 205, an authorization to proceed with an ATM transactionafter providing the user authentication credential, as described abovein connection with FIGS. 1A-1I.

As further shown in FIG. 5B, process 500 may include causing a secondprompt, for the user to select an ATM transaction type, to be presentedbased on obtaining the authorization (block 540). For example, userdevice 240 (e.g., using processor 320, memory 330, storage component340, output component 360, communication interface 370, and/or the like)may cause a second prompt, for the user to select an ATM transactiontype, to be presented based on obtaining the authorization, as describedabove in connection with FIGS. 1A-1I.

As further shown in FIG. 5B, process 500 may include detecting a userselection of a particular ATM transaction type after causing the secondprompt to be presented (block 545). For example, user device 240 (e.g.,using processor 320, memory 330, storage component 340, input component350, communication interface 370, and/or the like) may detect a userselection of a particular ATM transaction type after causing the secondprompt to be presented, as described above in connection with FIGS.1A-1I.

As further shown in FIG. 5B, process 500 may include providing, to theATM device, information regarding the particular ATM transaction type,based on detecting the user selection of the particular ATM transactiontype, to cause the ATM device to perform the ATM transaction (block550). For example, user device 240 (e.g., using processor 320, memory330, storage component 340, communication interface 370, and/or thelike) may provide, to ATM device 205, information regarding theparticular ATM transaction type, based on detecting the user selectionof the particular ATM transaction type, to cause ATM device 205 toperform the ATM transaction, as described above in connection with FIGS.1A-1I.

Process 500 may include additional implementations, such as any singleimplementation or any combination of implementations described belowand/or in connection with one or more other processes describedelsewhere herein.

In some implementations, the one or more instructions, when executed bythe one or more processors, may further cause the one or more processorsto provide, to the ATM device and prior to receiving the request for theuser authentication credential information, data relating to atransaction card (e.g., transaction card 250) that is associated withthe user.

In some implementations, the one or more instructions, that cause theone or more processors to receive the request, may cause the one or moreprocessors to receive the request based on detection, by the ATM device,of a presence of a transaction card (e.g., transaction card 250)associated with the user.

In some implementations, the particular ATM transaction type may relateto withdrawing financial instruments from the ATM device. In someimplementations, the one or more instructions, when executed by the oneor more processors, may further cause the one or more processors toreceive, from the ATM device, an instruction to prompt the user toobtain a financial instrument from the ATM device.

In some implementations, the particular ATM transaction type may relateto depositing financial instruments into the ATM device. In someimplementations, the one or more instructions, when executed by the oneor more processors, may further cause the one or more processors toreceive, from the ATM device, an instruction to prompt the user todeposit a financial instrument into the ATM device. In someimplementations, the ATM device may lack a display screen.

Although FIGS. 5A and 5B show example blocks of process 500, in someimplementations, process 500 may include additional blocks, fewerblocks, different blocks, or differently arranged blocks than thosedepicted in FIGS. 5A and 5B. Additionally, or alternatively, two or moreof the blocks of process 500 may be performed in parallel.

FIG. 6 is a flow chart of an example process 600 using an ATM device tointeract with a user device to facilitate a transaction. In someimplementations, one or more process blocks of FIG. 6 may be performedby ATM device 205. In some implementations, one or more process blocksof FIG. 6 may be performed by another device or a group of devicesseparate from or including ATM device 205, such as validation device230, user device 240, and/or transaction card 250.

In some implementations, an ATM device (e.g., ATM device 205) mayinclude a device body. In some implementations, the device body mayinclude a sync button to initiate wireless communications with externaluser devices (e.g., user devices 240). In some implementations, the ATMdevice may include a communication interface (e.g., communicationinterface 225, communication interface 370, and/or the like) configuredto communicatively couple to external user devices (e.g., user devices240) based on a user selection of the sync button, one or more memories(e.g., memory 220, memory 330, and/or the like), and one or moreprocessors (e.g., processor(s) 215, processor 320, and/or the like)communicatively coupled to the one or more memories and thecommunication interface. In some implementations, the one or moreprocessors may be configured to perform process 600.

As shown in FIG. 6, process 600 may include causing the communicationinterface to provide, to an external user device, a first instruction toprompt a user of the external user device to input PIN informationrelating to an account associated with the user (block 610). Forexample, ATM device 205 (e.g., using processor(s) 215, processor 320,memory 220, memory 330, storage component 340, and/or the like) maycause communication interface 225 and/or communication interface 370 toprovide, to an external user device (e.g., user device 240), a firstinstruction to prompt a user of the external user device to input PINinformation relating to an account associated with the user, asdescribed above in connection with FIGS. 1A-1I.

As further shown in FIG. 6, process 600 may include receiving, via thecommunication interface, a PIN provided by the external user deviceafter causing the communication interface to provide the firstinstruction (block 620). For example, ATM device 205 (e.g., usingprocessor(s) 215, processor 320, memory 220, memory 330, storagecomponent 340, and/or the like) may receive, via communication interface225 and/or communication interface 370, a PIN provided by the externaluser device (e.g., user device 240) after causing communicationinterface 225 and/or communication interface 370 to provide the firstinstruction, as described above in connection with FIGS. 1A-1I.

As further shown in FIG. 6, process 600 may include performing an actionto validate the PIN with respect to the account (block 630). Forexample, ATM device 205 (e.g., using processor(s) 215, processor 320,memory 220, memory 330, storage component 340, communication interface225, communication interface 370, and/or the like) may perform an actionto validate the PIN with respect to the account, as described above inconnection with FIGS. 1A-1I.

As further shown in FIG. 6, process 600 may include causing thecommunication interface to provide, to the external user device andbased on validating the PIN, a second instruction to prompt the user tospecify transaction information (block 640). For example, ATM device 205(e.g., using processor(s) 215, processor 320, memory 220, memory 330,storage component 340, and/or the like) may cause communicationinterface 225 and/or communication interface 370 to provide, to theexternal user device (e.g., user device 240) and based on validating thePIN, a second instruction to prompt the user to specify transactioninformation, as described above in connection with FIGS. 1A-1I.

As further shown in FIG. 6, process 600 may include performing an ATMtransaction based on the transaction information (block 650). Forexample, ATM device 205 (e.g., using processor(s) 215, processor 320,memory 220, memory 330, storage component 340, and/or the like) mayperform an ATM transaction based on the transaction information, asdescribed above in connection with FIGS. 1A-1I.

Process 600 may include additional implementations, such as any singleimplementation or any combination of implementations described belowand/or in connection with one or more other processes describedelsewhere herein.

In some implementations, the one or more processors, when causing thecommunication interface to provide the second instruction, may beconfigured to cause the communication interface to provide the secondinstruction to prompt the user to select an ATM transaction type. Insome implementations, the one or more processors may be furtherconfigured to receive a user selection of the sync button, and cause thecommunication interface to broadcast a pairing request based onreceiving the user selection of the sync button.

In some implementations, the one or more processors may be furtherconfigured to receive a pairing response from the external user deviceafter causing the communication interface to broadcast the pairingrequest, and cause the communication interface to establish acommunication session with the external user device based on receivingthe pairing response. In some implementations, the device body may lackany user interface components other than the sync button.

In some implementations, the ATM device may further include anadditional communication interface configured to detect contactlesstransaction cards located within a threshold distance from the ATMdevice. In some implementations, the one or more processors may befurther configured to receive, from the additional communicationinterface, an indication that a contactless transaction card is locatedwithin the threshold distance from the ATM device.

Although FIG. 6 shows example blocks of process 600, in someimplementations, process 600 may include additional blocks, fewerblocks, different blocks, or differently arranged blocks than thosedepicted in FIG. 6. Additionally, or alternatively, two or more of theblocks of process 600 may be performed in parallel.

Some implementations, described herein, provide a user device 240 thatis capable of functioning as a user interface for an ATM device 205. Insome implementations, user device 240 is capable of permitting a user toinput the user's authentication credential (e.g., personalidentification number (PIN)) and make ATM transaction selection(s), andproviding the authentication credential, and information regarding theATM transaction selection(s), to ATM device 205 to performtransaction(s). In some implementations, ATM device 205 lacks userinterface components, such as a touch screen display, a keypad, and/orthe like, that are typically included in an ATM device. In someimplementations, ATM device 205 may include a user-selectablesynchronization (“sync”) button that, when selected, enables ATM device205 to pair with user device 240, and one or more illuminationcomponents (e.g., light-emitting diodes (LEDs)) that may be used toprovide user notifications.

In this way, an ATM device manufacturer can provide an ATM device thatincludes fewer components, which simplifies the design and manufacturingof the ATM device, thereby reducing costs. In addition, this reduces oreliminates the possibility of wear and tear of the ATM device that wouldotherwise occur due to frequent user interaction with user interfacecomponents. Furthermore, enabling a user device (e.g., that is externalto an ATM device) to function as a user interface of the ATM devicereduces or eliminates a need for a user to input the user's PIN directlyto the ATM device, which reduces or eliminates the possibility of theft(e.g., via skimmers, cameras, and/or the like) of user account data andimproves the overall security of ATM transactions.

The foregoing disclosure provides illustration and description, but isnot intended to be exhaustive or to limit the implementations to theprecise form disclosed. Modifications and variations are possible inlight of the above disclosure or may be acquired from practice of theimplementations.

As used herein, the term component is intended to be broadly construedas hardware, firmware, or a combination of hardware and software.

Some implementations are described herein in connection with thresholds.As used herein, satisfying a threshold may refer to a value beinggreater than the threshold, more than the threshold, higher than thethreshold, greater than or equal to the threshold, less than thethreshold, fewer than the threshold, lower than the threshold, less thanor equal to the threshold, equal to the threshold, and/or the like.

Certain user interfaces have been described herein and/or shown in thefigures. A user interface may include a graphical user interface, anon-graphical user interface, a text-based user interface, and/or thelike. A user interface may provide information for display. In someimplementations, a user may interact with the information, such as byproviding input via an input component of a device that provides theuser interface for display. In some implementations, a user interfacemay be configurable by a device and/or a user (e.g., a user may changethe size of the user interface, information provided via the userinterface, a position of information provided via the user interface,etc.). Additionally, or alternatively, a user interface may bepre-configured to a standard configuration, a specific configurationbased on a type of device on which the user interface is displayed,and/or a set of configurations based on capabilities and/orspecifications associated with a device on which the user interface isdisplayed.

It will be apparent that systems and/or methods, described herein, maybe implemented in different forms of hardware, firmware, or acombination of hardware and software. The actual specialized controlhardware or software code used to implement these systems and/or methodsis not limiting of the implementations. Thus, the operation and behaviorof the systems and/or methods were described herein without reference tospecific software code—it being understood that software and hardwaremay be designed to implement the systems and/or methods based on thedescription herein.

Even though particular combinations of features are recited in theclaims and/or disclosed in the specification, these combinations are notintended to limit the disclosure of possible implementations. In fact,many of these features may be combined in ways not specifically recitedin the claims and/or disclosed in the specification. Although eachdependent claim listed below may directly depend on only one claim, thedisclosure of possible implementations includes each dependent claim incombination with every other claim in the claim set.

No element, act, or instruction used herein should be construed ascritical or essential unless explicitly described as such. Also, as usedherein, the articles “a” and “an” are intended to include one or moreitems, and may be used interchangeably with “one or more.” Furthermore,as used herein, the term “set” is intended to include one or more items(e.g., related items, unrelated items, a combination of related andunrelated items, etc.), and may be used interchangeably with “one ormore.” Where only one item is intended, the term “one” or similarlanguage is used. Also, as used herein, the terms “has,” “have,”“having,” and/or the like are intended to be open-ended terms. Further,the phrase “based on” is intended to mean “based, at least in part, on”unless explicitly stated otherwise.

What is claimed is:
 1. A method, comprising: receiving, by a userdevice, an indication that an automated teller machine (ATM) transactionis to be conducted, wherein the indication is received based ondetecting, by the user device, a presence of an ATM transaction card;displaying, by the user device, one or more prompts, for a user to inputuser authentication credential information, and to select an ATMtransaction type, based on receiving the indication; detecting, by theuser device, one or more user inputs that include a user authenticationcredential and a selection of a particular ATM transaction type afterdisplaying the one or more prompts; receiving, by the user device andfrom an ATM device, a request to establish a communication session afterdetecting the one or more user inputs, the ATM device including a syncbutton to initiate communicative coupling of the ATM device and the userdevice, and the request being based on a selection of the sync button;communicatively coupling, by the user device, to the ATM device based onreceiving the request; receiving, by the user device, from the ATMdevice, and via the communication session, data indicating that the ATMtransaction card has physically interfaced with the ATM device;providing, by the user device, to the ATM device, and based on receivingthe data indicating that the ATM transaction card has physicallyinterfaced with the ATM device and based on communicatively coupling tothe ATM device, the user authentication credential and data regardingthe particular ATM transaction type to cause the ATM device to performthe ATM transaction; and displaying, by the user device, informationregarding the ATM transaction after providing the user authenticationcredential and the data regarding the particular ATM transaction type.2. The method of claim 1, wherein receiving the indication comprises:receiving, by the user device, a user command to conduct the ATMtransaction using information associated with the ATM transaction card.3. The method of claim 1, further comprising: initiating a timer afterdetecting the one or more user inputs; determining whether the timer hasexpired prior to providing the user authentication credential and thedata regarding the particular ATM transaction type; and whereinproviding the user authentication credential and the data regarding theparticular ATM transaction type comprises: providing the userauthentication credential and the data regarding the particular ATMtransaction type further based on determining that the timer has notexpired.
 4. The method of claim 1, further comprising: receiving, fromthe ATM device, the information regarding the ATM transaction; andwherein displaying the information regarding the ATM transactioncomprises: displaying the information regarding the ATM transactionbased on receiving the information regarding the ATM transaction.
 5. Themethod of claim 1, wherein the information regarding the ATM transactioncomprises: an instruction to the user to insert one or more financialinstruments into the ATM device, or to retrieve one or more financialinstruments from the ATM device, depending on the particular ATMtransaction type.
 6. The method of claim 1, wherein detecting thepresence of the ATM transaction card comprises: detecting, by the userdevice, the presence of the ATM transaction card using near-fieldcommunication (NFC).
 7. The method of claim 1, further comprising:automatically executing an application of the user device based on alocation of the user device relative to the ATM device, the applicationbeing used to communicate with the ATM device.
 8. A non-transitorycomputer-readable medium storing instructions, the instructionscomprising: one or more instructions that, when executed by one or moreprocessors of a user device, cause the one or more processors to:receive an indication that an automated teller machine (ATM) transactionis to be conducted, wherein the indication is received based ondetecting, by the user device, a presence of an ATM transaction card;display one or more prompts, for a user to input user authenticationcredential information, and to select an ATM transaction type, based onreceiving the indication; detect one or more user inputs that include auser authentication credential and a selection of a particular ATMtransaction type after displaying the one or more prompts; receive, froman ATM device, a request to establish a communication session afterdetecting the one or more user inputs, the ATM device including a syncbutton to initiate communicative coupling of the ATM device and the userdevice, and the request being based on a selection of the sync button;communicatively couple to the ATM device based on receiving the request;receive, from the ATM device, and via the communication session, dataindicating that the ATM transaction card has physically interfaced withthe ATM device; provide, to the ATM device, and based on receiving thedata indicating that the ATM transaction card has physically interfacedwith the ATM device and based on communicatively coupling to the ATMdevice, the user authentication credential and data regarding theparticular ATM transaction type to cause the ATM device to perform theATM transaction; and display information regarding the ATM transactionafter providing the user authentication credential and the dataregarding the particular ATM transaction type.
 9. The non-transitorycomputer-readable medium of claim 8, wherein the one or moreinstructions, when executed by the one or more processors, further causethe one or more processors to: provide, to the ATM device, data relatingto the ATM transaction card.
 10. The non-transitory computer-readablemedium of claim 8, wherein the one or more instructions, when executedby the one or more processors, further cause the one or more processorsto: initiate a timer after detecting the one or more user inputs; anddetermine whether the timer has expired prior to providing the userauthentication credential and the data regarding the particular ATMtransaction type.
 11. The non-transitory computer-readable medium ofclaim 8, wherein the particular ATM transaction type relates towithdrawing financial instruments from the ATM device; and wherein theone or more instructions, when executed by the one or more processors,further cause the one or more processors to: receive, from the ATMdevice, an instruction to prompt the user to obtain a financialinstrument from the ATM device.
 12. The non-transitory computer-readablemedium of claim 8, wherein the particular ATM transaction type relatesto depositing financial instruments into the ATM device; and wherein theone or more instructions, when executed by the one or more processors,further cause the one or more processors to: receive, from the ATMdevice, an instruction to prompt the user to deposit a financialinstrument into the ATM device.
 13. The non-transitory computer-readablemedium of claim 8, wherein the information regarding the ATM transactioncomprises: an instruction to the user to insert one or more financialinstruments into the ATM device, or to retrieve one or more financialinstruments from the ATM device, depending on the particular ATMtransaction type.
 14. A device, comprising: one or more memories; andone or more processors, communicatively coupled to the one or morememories, to: receive an indication that an automated teller machine(ATM) transaction is to be conducted, wherein the indication is receivedbased on detecting, by the device, a presence of an ATM transactioncard; display one or more prompts, for a user to input userauthentication credential information, and to select an ATM transactiontype, based on receiving the indication; detect one or more user inputsthat include a user authentication credential and a selection of aparticular ATM transaction type after displaying the one or moreprompts; receive, from an ATM device, a request to establish acommunication session after detecting the one or more user inputs, theATM device including a sync button to initiate communicative coupling ofthe ATM device and the device, and the request being based on aselection of the sync button; communicatively couple to the ATM devicebased on receiving the request; receive, by the user device, from theATM device, and via the communication session, data indicating that theATM transaction card has physically interfaced with the ATM device;provide, to the ATM device, and based on receiving the data indicatingthat the ATM transaction card has physically interfaced with the ATMdevice and based on communicatively coupling to the ATM device, the userauthentication credential and data regarding the particular ATMtransaction type to cause the ATM device to perform the ATM transaction;and display information regarding the ATM transaction after providingthe user authentication credential and the data regarding the particularATM transaction type.
 15. The device of claim 14, wherein the one ormore processors, when receiving the indication, are to: receive a usercommand to conduct the ATM transaction using information associated withthe ATM transaction card.
 16. The device of claim 14, wherein the one ormore processors are further to: initiate a timer after detecting the oneor more user inputs; and determine whether the timer has expired priorto providing the user authentication credential and the data regardingthe particular ATM transaction type.
 17. The device of claim 14, whereinthe one or more processors are further to: receive, from the ATM device,the information regarding the ATM transaction; and wherein the one ormore processors, when displaying the information regarding the ATMtransaction, are to: display the information regarding the ATMtransaction based on receiving the information regarding the ATMtransaction.
 18. The device of claim 14, wherein the informationregarding the ATM transaction comprises: an instruction to the user toinsert one or more financial instruments into the ATM device, or toretrieve one or more financial instruments from the ATM device,depending on the particular ATM transaction type.
 19. The device ofclaim 14, wherein the particular ATM transaction type relates towithdrawing financial instruments from the ATM device; and wherein theone or more processors are further to: receive, from the ATM device, aninstruction to prompt the user to obtain a financial instrument from theATM device.
 20. The device of claim 14, wherein the particular ATMtransaction type relates to depositing financial instruments into theATM device; and wherein the one or more processors are further to:receive, from the ATM device, an instruction to prompt the user todeposit a financial instrument into the ATM device.